---
type: guide
title: Getting Started
description: How to work in this vault — write concepts, track tasks, and keep the format honest.
tags: [guide]
timestamp: {{DATE}}
---
<!-- ✂ docujoint template sample — replace with your own content, then delete this comment. -->
# Getting Started

## Overview
This vault follows the format declared in `format.yaml`. Every document is one
concept with `type`, `title` and `description` frontmatter; links are markdown
paths from the vault root, like [Example Concept](</Concepts/Example Concept.md>);
`[[wikilinks]]` are forbidden. Sections you don't declare are free-form —
write whatever the document needs.

## Steps
1. Write a concept: copy [Example Concept](</Concepts/Example Concept.md>), set its frontmatter, link it from other docs.
2. Run `dj lint --all --vault vault --format format.yaml` — errors break the parser, warnings mean incomplete.
3. Run `dj index --vault vault --format format.yaml --write` so the catalogue lists your new concept.
4. Run `dj dashboard --vault vault --format format.yaml --dashboard dashboard.yaml --out dashboard.html` and open it.

## Tasks
The state column you might expect is deliberately missing — state is **derived**
from Done + Blocked, so it can never contradict what is written.

| ID | Task | Done | Blocked |
|----|------|------|---------|
| t1 | Write your first concept | Worked example shipped as [Example Concept](</Concepts/Example Concept.md>) — repo://my-docs/vault/Concepts/Example%20Concept.md · test://my-docs/format.test.ts | — |
| t2 | Connect an artifact inventory | — | Run `dj scan --source my-docs=. --out artifacts.json` over your own checkouts, then gate with `dj lint --all --inventory artifacts.json` |
| t3 | Customise the dashboard | — | — |

## Open questions
Questions live inside the concept they belong to, in a table the engine parses.

| Q | Question | About | Status | Resolution |
|---|----------|-------|--------|------------|
| q1 | Which URI schemes should our evidence use? | t2 | open |  |